Improve Callbacks - #191
Conversation
…d pairs & Symbol --> String & KHist require Float64
|
AbstractMCMC.jl documentation for PR #191 is available at: |
yebai
left a comment
There was a problem hiding this comment.
Looks very good, @shravanngoswamii. One last refactoring comment!
|
Can I request that you merge this into a branch that is not On the Turing.jl PR can you use https://pkgdocs.julialang.org/v1/toml-files/#The-%5Bsources%5D-section to point to the unreleased branch of AbstractMCMC? I want to avoid a situation where we do stuff on Turing, realise that something here needs to be changed, and then you have to make a breaking release on AbstractMCMC to fix it. Once the Turing code is fine then we can release a new minor version here. |
We kept them separate based on @yebai's suggestion to distinguish between step-level statistics and "extras" (hyperparameters). |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…tractMCMC.jl into callbacks-updates
yebai
left a comment
There was a problem hiding this comment.
Excellent work, thanks @shravanngoswamii!
penelopeysm
left a comment
There was a problem hiding this comment.
Thanks! Final comment: please push a new branch to the repo that has the same state as main, maybe call it callbacks or something, and change the base branch of this PR to be that. Then I'm happy to merge.
|
@penelopeysm, since this PR isn't breaking and other research work depends on it, are you happy if we merge it to |
|
No not really, because I would rather not find out that there's something that needs to be changed in the interface, and then having to release a breaking version of AbstractMCMC.
Am I missing something, or is it just the Turing PR? If it's just the Turing PR, as I said in my last comment somewhere up there, you can use This is what Markus and I have been doing for DPPL releases for quite a while now. |
|
(If you're like, absolutely, 100%, certain that the interface is final and it will not need to be changed, then sure merge to main and release -- but I don't have that confidence myself.) |
|
It's very helpful for some MCMC research work : ) Let's be slightly more flexible here, since |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #191 +/- ##
===========================
===========================
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Happy to iterate on it anytime! |
No description provided.